Software Requirements Specification
A Software Requirements Specification ('SRS) – a requirements specification for a software system – is a complete description of the behavior of a system to be developed. It includes a set of use cases that describe all the interactions the users will have with the software. In addition to use cases, the SRS also contains non-functional requirements. Non-functional requirements are requirements which impose constraints on the design or implementation (such as performance engineering requirements, quality standards, or design constraints).
Software Requirements is a sub-field of Software engineering that deals with the elicitation, analysis, specification, and validation of requirements for software.[1]
The software requirement specification (SRS) document enlists all necessary requirements for project development. To derive the requirements we need to have clear and thorough understanding of the products to be developed. This is prepared after detailed communications with project team and the customer. A general organization of an SRS is as follows [2]
- Introduction
- Purpose
- Scope
- Definitions
- System Overview
- References
- Overall Description
- Product Perspective
- Product Functions
- User Characteristics
- Constraints, Assumptions and Dependencies
- Specific Requirements
- External interfaces
- Functions
- Performance requirements
- Logical database requirement
- Design constraints
- Key features
See also
References
External links
|
|
Fields |
|
|
Concepts |
|
|
Orientations |
|
|
Models |
Development models
|
|
|
Other models
|
|
|
Modeling languages
|
|
|
|
Software
engineers |
|
|
Related fields |
|
|
|
|
|
|
Current |
|
|
802 series |
- 802
- .1 (p, Q, Qat, Qay, X, ad, AE, ag, ah, ak, aq)
- .2
- .3
- .4
- .5
- .6
- .7
- .8
- .9
- .10
- .11 (a b d e f g h i j k n p r s u v w y ac)
- .12
- .15
- .15.4
- .15.4a
- .16
- .18
- .20
- .21
- .22
|
|
Proposed |
|
|
Superseded |
|
|
|
|